View SRTAG2KL_9004691.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

this is preliminary information on a new product now in dev elopment or undergoing evaluati on. details are subject to change without notice. january 2015 docid026583 rev 2 1/51 1 SRTAG2KL nfc forum type 4 tag ic with 2-kbit eeprom datasheet - preliminary data features contactless interface ? nfc forum type 4 tag ? iso/iec 14443 type a ? 106 kbps data rate ? internal tuning capacitance: 50 pf memory ? 256-byte (2-kbit) eeprom ? support of ndef data structure ? data retention: 200 years ? endurance: 1 million erase-write cycles ? read up to 255 bytes in a single command ? write up to 54 bytes in a single command ? chaining capability ? 7 bytes unique identifier (uid) ? 128 bits passwords protection ? 20 bits event counter with anti-tearing description the SRTAG2KL device is a nfc tag ic. it embeds an eeprom memory. it can be operated from a 13.56 mhz rfid reader or an nfc phone. the SRTAG2KL is an nfc forum type 4 tag; it communicates using the iso/iec 14443 type a protocol. wafer (sb12i) www.st.com
contents SRTAG2KL 2/51 docid026583 rev 2 contents 1 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 functional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.1.1 tag mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.1 antenna coil (ac0, ac1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3 SRTAG2KL memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1 memory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 3.1.1 file identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1.2 cc file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1.3 ndef file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1.4 system file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2 read and write access rights to the ndef file . . . . . . . . . . . . . . . . . . . . 13 3.2.1 state of the read and write access rights . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.2 changing the read access right to ndef files . . . . . . . . . . . . . . . . . . . . 14 3.2.3 changing the write access right to ndef files . . . . . . . . . . . . . . . . . . . 15 3.3 access right life time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.4 ndef file passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.5 read/write counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4 communication mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 4.1 master and slave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5 rf command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1 structure of the command sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.2 i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.2.1 c-apdu: payload format of a command . . . . . . . . . . . . . . . . . . . . . . . . 22 5.2.2 r-apdu: payload format of a response . . . . . . . . . . . . . . . . . . . . . . . . 22 5.3 r-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.4 s-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.5 crc of the rf frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6 nfc forum type 4 tag protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
docid026583 rev 2 3/51 SRTAG2KL contents 5.6.1 commands set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.6.2 status and error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.6.3 ndef tag application select command . . . . . . . . . . . . . . . . . . . . . . . . 27 5.6.4 capability container select command . . . . . . . . . . . . . . . . . . . . . . . . . . 27 5.6.5 ndef select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 5.6.6 system file select command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.6.7 readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 5.6.8 updatebinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.7 iso/iec 7816-4 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.7.1 verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.7.2 change reference data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 5.7.3 enable verification requirement command . . . . . . . . . . . . . . . . . . . . . . 34 5.7.4 disable verification requirement command . . . . . . . . . . . . . . . . . . . . . 35 5.8 st proprietary command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.8.1 extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.8.2 enablepermanentstate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.9 specific rf command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.9.1 anticollision command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5.9.2 rats command and ats response . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.9.3 pps command & response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 6 rf device operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.1 anticollision and device activation command set for the rf interface . . 43 6.2 open an rfsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.3 close an rfsession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.4 applicative command set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 7 functional procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.1 selection of an ndef message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.2 reading of an ndef message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.3 reading a locked ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.4 locking an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 7.5 unlocking an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.6 reaching the read-only state for an ndef file . . . . . . . . . . . . . . . . . . . . . 45 7.7 changing a file type procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
contents SRTAG2KL 4/51 docid026583 rev 2 8 uid: unique identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 9 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 10 rf electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 11 part numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 12 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
docid026583 rev 2 5/51 SRTAG2KL list of tables list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 2. functional mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 3. file identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 table 4. cc file layout for 1 ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 table 5. ndef file layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 table 6. field list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 7. details about the counter config field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 8. read access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 9. write access right . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 10. rf command sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 11. i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 12. pcb field of the i-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 13. c-apdu format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 14. r-apdu format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 table 15. r-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 16. r-block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 17. s-block format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 18. s-block detailed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 19. command set overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 20. status code of the SRTAG2KL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 21. error code of the SRTAG2KL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 22. c-apdu of the ndef tag applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 23. r-apdu of the ndef tag applic ation select command . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 24. c-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 25. r-apdu of the capability container sele ct command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 26. c-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 27. r-apdu of the ndef select comman d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 28. c-apdu of the system file sele ct command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 29. r-apdu of the system file sele ct command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 30. c-apdu of the readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 31. r-apdu of the readbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 32. c-apdu of the updatebinary comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 33. r-apdu of the updatebinary comma nd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 34. verify command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 35. r-apdu of the verify command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 36. change reference data command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 table 37. r-apdu of the change reference data command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 38. enable verification requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 table 39. r-apdu of the enable verification requirement co mmand. . . . . . . . . . . . . . . . . . . . . . . . 35 table 40. disable verification requirement command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 41. r-apdu of the disable verification requirement command . . . . . . . . . . . . . . . . . . . . . . . 36 table 42. c-apdu of the extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 table 43. r-apdu of the extendedreadbinary command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 44. enablepermanentstate command format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 45. r-apdu table of the enablepermanentstate comman d . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 46. commands issues by the rf host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 8 table 47. example of anticollision sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 48. rats command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
list of tables SRTAG2KL 6/51 docid026583 rev 2 table 49. conversion from fdsi to fsd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 50. ats response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 table 51. pps command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 52. ascending and descending data rate coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 table 53. pps response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 table 54. uid format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 table 55. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 table 56. default operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 57. rf characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 58. ordering information scheme for packaged devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 59. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
docid026583 rev 2 7/51 SRTAG2KL list of figures list of figures figure 1. SRTAG2KL block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 figure 2. changing the read access right to an ndef file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 figure 3. changing the write access right to an ndef file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
functional description SRTAG2KL 8/51 docid026583 rev 2 1 functional description the SRTAG2KL device is a nfc tag that can be accessed from the rf interface. the rf interface is based on the iso/iec 14443 type a standard. the SRTAG2KL is compatible with the nfc forum type 4 tag specifications and supports all corresponding commands. figure 1 displays the block diagram of the SRTAG2KL device. figure 1. SRTAG2KL block diagram 06y9 5)lqwhuidfh edvhgrq ,62,(& 7\sh$ vwdqgdug $& $& 3rzhu pdqdjhphqw xqlw h/?????u ? h??uu}?? $qdorj)urqwhqg edvhgrq ,62,(& 7\sh$vwdqgdug ,qwhuqdowxqlqj fdsdflwdqfh 'ljlwdoxqlw 1)&)ruxp 7\sh7dj surwrfro
docid026583 rev 2 9/51 SRTAG2KL functional description 1.1 functional mode the SRTAG2KL has just one functional mode available (see table 2 ). 1.1.1 tag mode the SRTAG2KL is supplied by the rf field and can communicate with an rf host (rfid reader or an nfc phone). the user memory can be accessed by the rf commands. table 1. signal names signal name function direction ac0, ac1 antenna coils - table 2. functional mode mode supply source comments tag mode rf field only the rf interface operate only when rf field level is sufficient.
signal descriptions SRTAG2KL 10/51 docid026583 rev 2 2 signal descriptions 2.1 antenna coil (ac0, ac1) these inputs are used to connect the device to an external coil exclusively. it is advised not to connect any other dc or ac path to ac0 or ac1. when correctly tuned, the coil is used to access the device using nfc forum type 4 commands.
docid026583 rev 2 11/51 SRTAG2KL SRTAG2KL memory management 3 SRTAG2KL memory management 3.1 memory structure the SRTAG2KL supports the ndef tag application as defined in the nfc forum type 4 tag. the SRTAG2KL is composed of three files: ? one capability container file ? one ndef file ? one system file: this file is an st-proprietary file the system file contains some information on the configuration of the SRTAG2KL device. the cc file gives some information about the SRTAG2KL itself and the ndef file. the ndef file contains the user data. 3.1.1 file identifier the file identifier is the value used in the select command to select a file. 3.1.2 cc file layout the cc file gives some information about the SRTAG2KL and the ndef file. this file is a read-only file for the rf host and cannot be modified by issuing a write command. the t field, read access and write access fiel ds can be changed by the rf host by issuing a specific process (refer to section 7: functional procedures ). table 3. file identifier file identifier meaning 0xe101 system file 0xe103 cc file 0x0001 ndef file table 4. cc file layout for 1 ndef file file offset meaning value comments 0x0000 length cc file 0x000f 15 bytes 0x0002 mapping version (1) 0x20 or 0x10 v 2.0 or v 1.0 0x0003 maximum number of bytes that can be read 0x00ff 255 bytes 0x0005 maximum number of bytes t hat can be written 0x0036 54 bytes
SRTAG2KL memory management SRTAG2KL 12/51 docid026583 rev 2 3.1.3 ndef file layout the ndef file contains the ndef message whic h contains the user data. the rf host can read and write data inside the file. the first two bytes named ndef message length define the size of the ndef message. the ndef message length shall be managed by the application and the SRTAG2KL device does not ch eck if its value is relevant vs the data written by the rf host. the SRTAG2KL device uses the ndef message length, e. g. the standard read can be processed only inside the ndef message; otherwise, the SRTAG2KL device returns an error code. for more details about the read command, refer to section 5.6.7: readbinary command . 0x0007 ndef file control tlv 0x04 (2) t field 0x0008 0x06 l field 0x0009 0x0001 fileid 0x000b 0x0100 maximum ndef file size in byte 0x000d 0x00 (2) read access 0x000e 0x00 (2) write access 1. according to the reader command format SRTAG2KL will automatically align to the corresponding nfc forum version. 2. delivery state. table 4. cc file layout for 1 ndef file (continued) file offset meaning value comments table 5. ndef file layout file offset byte 0 byte 1 byte 2 byte 3 0x0000 ndef message length user data user data 0x0004 user data user data user data user data ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... 0x00fc ... ... ... user data
docid026583 rev 2 13/51 SRTAG2KL SRTAG2KL memory management 3.1.4 system file layout the system file specifies the configuration of the SRTAG2KL. table 6 lists the different fields. 3.2 read and write access rights to the ndef file the ndef file can be locked for read or writ e accesses. it is also protected by a 128-bit password that the host shall present before accessing the ndef file. there are two 128-bit passwords, one for the read access and the other one for the write access. table 6. field list file offset field name number of bytes read access write access delivery state 0x0000 length system file 2 yes - 0x0012 0x0002 st reserved 1 yes none 0x80 0x0003 event counter config 1 yes yes (1) 1. configuration bytes can be locked by setting the most significant bit to 1. once locked, these bytes cannot be changed anymore. 0x00 0x0004 20 bits counter (ms nibble 0x0) 3 yes none 0x000000 0x0007 product version 1 yes none 0x11 (2) 2. st reserved. 0x0008 uid 7 yes none 0x02e2 xx xx xx xx xx (3) 3. x values are defined by st to ensure uid unicity. 0x000f memory size - 1 2 yes none 0x00ff 0x0011 product code 1 yes none 0xe2 table 7. details about the counter config field file offset b7 b6-b2 b1 b0 0x0003 counter config lock bit: 0b0: unlocked 0b1: locked 0b00000: st reserved counter enable: 0b0: disable 0b1: enable counter increment: 0b0: on read 0b1: on write
SRTAG2KL memory management SRTAG2KL 14/51 docid026583 rev 2 an ndef file can be permanently locked for read or write accesses. thus, the host cannot access the ndef file. the read password shall be sent to the SRTAG2KL device before reading a read-locked ndef file. the write password shall be present on the srta g2kl device before writing a write-locked ndef file. the write password shall be sent to change the read or write access. the read or write access right is defined for the ndef file. 3.2.1 state of the read and write access rights two bytes in the cc file are used to define the read and write access rights to the ndef file. for more details, refer to section 3.1.2: cc file layout . the state 0xff and 0xfe cannot be changed by using the read or write passwords. 3.2.2 changing the read access right to ndef files the state diagram on figure 2 shows how to change the access right to read an ndef file. table 8. read access right value meaning 0x00 read access without any security 0x80 locked (1) 1. the read password shall be sent before reading in the ndef file. 0xfe read not authorized table 9. write access right value meaning 0x00 write access without any security 0x80 locked (1) 1. the write password shall be sent before writing in the ndef file. 0xff write not authorized
docid026583 rev 2 15/51 SRTAG2KL SRTAG2KL memory management figure 2. changing the read access right to an ndef file 1. see the procedure to lock the read access ( section 7.4: locking an ndef file ). 2. see the procedure to unlock the read access ( section 7.5: unlocking an ndef file ). 3. see the procedure to permanently lock the read access ( section 7.6: reaching the read-only state for an ndef file ). 4. proprietary state, not defined by nfc forum type 4 tag. 3.2.3 changing the write access right to ndef files the state diagram on figure 3 shows how to change the write access right to an ndef file. figure 3. changing the write access right to an ndef file 1. see the procedure to lock the write access. 2. see the procedure to unlock the write access. 3. see the procedure to permanently lock the write access ( section 7.6: reaching the read-only state for an ndef file ). 4. proprietary state, not defined by nfc forum type 4 tag. 069 3hupdqhqwo\orfnwkh1'()iloh [ [ [)( /rfnwkh1'()iloh 8qorfnwkh1'()iloh 069 [ [ [)) /rfnwkh1'()iloh 8qorfnwkh1'()iloh 3hupdqhqwo\orfnwkh1'()iloh
SRTAG2KL memory management SRTAG2KL 16/51 docid026583 rev 2 3.3 access right life time the access right life time is validated while the nd ef file is selected or until the end of the rf session. once the read or write access right is granted, the host can send one or more readbinary or updatebinary commands. at the end of a session or when the host selects another file, the read and write access rights are initialized. 3.4 ndef file passwords the ndef file passwords protect the read or write access from an rf interface from/to an ndef file. two ndef file passwords are av ailable for each ndef file: ? read password ? write password the length of a password is 128 bits (16 bytes). note: the delivery state for all passwords = 0x00000000000000000000000000000000. 3.5 read/write counter a 20 bits counter can track the read or write events on the ndef file. it benefits from an anti-tearing mechanism, that ensures the consistency of the counter, even if there has been an electrical problem during its increment. the value of the read/write counter can be che cked by any application, by reading suitable bytes in system file (see section 3.1.4 ). if enabled, the read/write coun ter will be incremented on first event (exclusively read or write) which is performed on the ndef file, insi de an rf session (an rf session is entered when SRTAG2KL receives a valid "select application" command). the counter is reset when it is disabled. apart from these procedures, there is no way to act on the value of this counter. the read/write counter can be configured through a specific byte in system file (see section 3.1.4 ). this configuration byte allows to: ? enable or disable this counter ? define if the counter must be increm ented on a read or write sequence ? definitively lock this configuration byte warning: once this configuration byte is locked, it cannot be changed anymore: the counter will behave accordingly.
docid026583 rev 2 17/51 SRTAG2KL SRTAG2KL memory management if enabled, the read/write coun ter will have an impact on the execution time of the event which is countered: the counte r increment needs some writ e cycles of specific eeprom cells automatically managed by SRTAG2KL, which increase the total time before the response is sent to the reader. as a consequence, an s(wtx) request can be issued on the comma nd that will increment the counter (see section 5.4 ).
communication mechanism SRTAG2KL 18/51 docid026583 rev 2 4 communication mechanism this chapter describes the principle of communication between an rf host and the SRTAG2KL device. 4.1 master and slave the SRTAG2KL acts as a slave device on the rf channel and therefore waits for a command from the rf host before sending its response. the rf host shall generate the rf field and the rf commands.
docid026583 rev 2 19/51 SRTAG2KL rf command sets 5 rf command sets this section describes the SRTAG2KL command sets that can be issued by the rf host. there are th ree command families: ? the nfc forum type 4 tag command set ? the iso/iec 7816-4 command set ? the proprietary command set the nfc forum type 4 tag command set and the iso/iec 7816-4 command set use the i- block format. for more details about the i-block format, refer to section 5.2: i-block format . two other command formats exist: ? the commands using the r-block format ? the commands using the s-block format for more details about these formats, refer to the corresponding sections: section 5.3: r- block format and section 5.4: s-block format . this section gives a brief description of the rf host commands. the format of these command sets is the i-block format. table 10 lists the rf command sets. table 10. rf command sets family command set command name class byte instruction code brief description nfc forum type 4 tag ndef tag application select 0x00 0xa4 ndef tag application select cc select 0x00 0xa4 select the cc file ndef select 0x00 0xa4 select the ndef file system select 0x00 0xa4 select the system file readbinary 0x00 0xb0 read data from file updatebinary 0x00 0xd6 write or erase data to a ndef file iso/iec 7816-4 verify 0x00 0x20 checks the right access of a ndef file or sends a password changereferencedata 0x00 0x24 change a read or write password enableverificationrequirement 0x00 0x28 activate the password security disableverificationrequirement 0x00 0x26 disable the password security st proprietary enablepermanentstate 0xa2 0x28 enables the read only or write only security state st proprietary extendedreadbinary 0xa2 0xb0 read data from file
rf command sets SRTAG2KL 20/51 docid026583 rev 2 5.1 structure of the command sets the exchange of data between the rf host and the SRTAG2KL uses three kinds of data formats, called blocks: ? i-block (information block): to exchange the command and the response ? r-block (receive ready block): to exchange positive or negative acknowledgement ? s-block (supervisory block): to use either the deselect command or the frame waiting extension (wtx) command or response this section describes the structure of i-block, r-block and s-block. this format is used for the application command set. 5.2 i-block format the i-block is used to exchange data between the rf host and the SRTAG2KL. it is composed of three fields. table 11 details the i-block format. table 11. i-block format name sod payload eod pcb did - crc length 1 byte 1 byte 1 to 251 bytes 2 bytes pcb field did field (optional) rf host to SRTAG2KL: c-apdu SRTAG2KL to rf host: r-apdu 2 crc bytes
docid026583 rev 2 21/51 SRTAG2KL rf command sets note: block numbering rules: when the rf host sends a command to the srta g2kl the format of the payload is the c- apdu. when the SRTAG2KL sends a command to the rf host, the format of the payload is the r- apdu. table 12. pcb field of the i-block format b7-b6b5b4b3b2b1b0 0b00 0 0 x 0 1 x i-block rfu must be set to 0 did field is present, if bit is set must be set to 0 must be set to 1 block number (1) 1. follow iso 14443_4 block numbering rules (see note) reader rules: rule a: the reader block numb er shall be initialized to 0. rule b: when an i-block or an r(ack) block with a block number equal to the current block number is received, the reader shall toggle the current block number before optionally sending a block to the SRTAG2KL. SRTAG2KL rules: rule c. the SRTAG2KL block number shall be initialized to 1 at activation. rule d. when an i-block is received, the SRTAG2KL shall toggle its block number before sending a block. note: the SRTAG2KL may check if the receiv ed block number is not in compliance with reader rules to decide neither to toggle its internal block number nor to send a response block. rule e. when an r(ack) block with a block number not equal to the current SRTAG2KL block number is received , the SRTAG2KL shall toggle its block number before sending a block. note: there is no block number toggling when an r(nak) block is received.
rf command sets SRTAG2KL 22/51 docid026583 rev 2 5.2.1 c-apdu: payload format of a command the c-apdu format is used by the rf host to send a command to the SRTAG2KL. table 13 describes its format. 5.2.2 r-apdu: payload format of a response the SRTAG2KL uses the i-block format to reply to a command which used the i-block format. this format is described in table 14 . 5.3 r-block format the r-block is used to convey positive or negative acknowledgment between the rf host and the SRTAG2KL. table 13. c-apdu format name payload field cla ins p1 p2 l c data le length 1 byte 1 byte 1 byte 1 byte 1 byte lc byte 1 byte class byte 0x00: standard command 0xa2: st command (1) 1. see table 10 instruction byte param byte 1 param byte 2 number of bytes of the data field data bytes number of bytes to be re ad in the SRTAG2KL memory table 14. r-apdu format name payload field data (optional) sw1 sw2 length le byte 1 byte 1 byte data status byte 1 status byte 2
docid026583 rev 2 23/51 SRTAG2KL rf command sets there are two kinds of r-blocks: ? r(ack): the acknowledgment block sent by the rf host or by the SRTAG2KL ? r( nak ): the non-acknowledgment block sent by the rf host table 15. r-block format nfc frame sod eod pcb did payload crc length 1 byte 1 byte 0 byte 2 bytes r(ack) without the did field: 0xa2 or 0xa3 r(ack) with the did field: 0xaa or 0xab r(nak) without the did field: 0xb2 or 0xb3 r(nak) with the did field: 0xba or 0xbb did field (optional) - 2 crc bytes
rf command sets SRTAG2KL 24/51 docid026583 rev 2 5.4 s-block format the s-block is used to exchange control information between a reader and a contactless tag. there are two requests using the s-block format: ? s(des): the deselect command ? s(wtx): the waiting frame extension command or response. a waiting time extension request occurs in rf when the operating time needed by SRTAG2KL is greater than 19.2 ms. the wtx field indicates the increase time factor to be used in this command execution (fdttemp = wtx * 19.2 ms). wtx depends on fwi. table 16. r-block detailed format b7-b6b5b4b3b2b1b0 0b10 1 x x 0 0 x r-block must be set to 1. 0: nak 1: ack 0: did field is not present 1: did field is present must be set to 0 must be set to 0 block number table 17. s-block format nfc frame sod eod pcb did payload crc length 1 byte 1 byte 1 byte 2 bytes 0xc2: for s(des) when the did field is not present 0xca: for s(des) when the did field is present 0xf2: for s(wtx) when the did field is not present 0xfa: for s(wtx) when the did field is present did field (optional) wtx field (optional) (1) 1. this field is present when b5-b4 bits ar e set to 0b11 (s-block is a wtx). see table 18: s-block detailed format . 2 crc bytes
docid026583 rev 2 25/51 SRTAG2KL rf command sets note: after receiving the deselect command, the session is released and SRTAG2KL enters the standby power mode. in response to a rats command, SRTAG2KL returns fwi parameter (default frame waiting time used); when SRTAG2KL needs more time for a command execution, it requests a frame waiting time extension by responding 0xf2 0xwtx (request waiting time = fwi * wtx). if the reader accepts SRTAG2KL request, it ac knowledges by sendin g the command 0xf2 0xwtx. the frame waiting time becomes fwi * wtx for the current command only. 5.5 crc of the rf frame the two crc bytes check the data transmission between the rf host and the SRTAG2KL. for the rf frame, the crc is computed on all th e data bits in the frame, excluding parity bits, sof and eof, and the crc itself. the crc is as defined in iso/iec 13239. the initial register content shall be 0x6363 and the register content shall not be inverted after calculation. 5.6 nfc forum type 4 tag protocol 5.6.1 commands set SRTAG2KL command set is built to easily support the nfc forum type 4 tag protocol. table 18. s-block detailed format b7-b6 b5-b4 b3 b2 b1 b0 0b11 x x 0 1 0 s-block 0b00: deselect 0b11: wtx 0: did field is not present 1: did field is present must be set to 0 must be set to 1 must be set to 0 table 19. command set overview command name brief description ndef tag application select select the ndef tag application capability container select select the capability container (cc) file using the select command ndef select select the ndef file using the select command. system file select select the system file using the select command.
rf command sets SRTAG2KL 26/51 docid026583 rev 2 5.6.2 status and error codes this section lists the status and the error code of the SRTAG2KL. readbinary read data from a file updatebinary write new data to a file table 19. command set overview (continued) command name brief description table 20. status code of the SRTAG2KL sw1 sw2 comment value 0x90 0x00 command completed successfully table 21. error code of the SRTAG2KL sw1 sw2 comment length 1 byte 1 byte value 0x62 0x82 end of file or record reached before reading le bytes value 0x63 0x00 password is required value 0x63 0xcx password is incorrect, x further retries allowed (x can take value 0,1, 2) value 0x65 0x81 unsuccessful updating value 0x67 0x00 wrong frame length value 0x69 0x81 cmd is incompatible with the file structure value 0x69 0x82 security status not satisfied value 0x69 0x84 reference data not usable value 0x6a 0x80 incorrect parameters le or lc value 0x6a 0x82 file or application not found value 0x6a 0x84 file overflow (lc error) value 0x6a 0x86 incorrect p1 or p2 values value 0x6d 0x00 ins field not supported value 0x6e 0x00 class not supported
docid026583 rev 2 27/51 SRTAG2KL rf command sets 5.6.3 ndef tag applic ation select command the rf host shall send this command to activate the ndef tag application. to activate the ndef tag application, the rf host sends the select command (see table 22 ) in addition to the sequence define d in the nfc forum digital protocol. table 22 defines the c-apdu of the select command to select the ndef tag application (called ndef tag application select). table 23 defines the r-apdu of the ndef tag application select command. note: for further return code s and definitions, refer to section 5.6.2: status and error codes . 5.6.4 capability cont ainer select command the rf host uses the capability container se lect procedure to se lect the capability container (cc) file. the cc file is selected when this command re turns "command completed" in the r-apdu. table 24 defines the c-apdu of the se lect command to select the cc file (called capability container select). table 22. c-apdu of the ndef tag application select command name cla ins p1 p2 lc data le 0x00 0xa4 0x04 0x00 0x07 0xd27600 00850101 0x00 class byte select instruction code p1 field p2 field number of bytes of data application id le field table 23. r-apdu of the ndef tag application select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 ndef tag application not found value - 0x6d 0x00 class not supported
rf command sets SRTAG2KL 28/51 docid026583 rev 2 table 25 defines the r-apdu of the cc select command. note: for further return code s and definitions, refer to section 5.6.2: status and error codes . 5.6.5 ndef select command the rf host uses the ndef select command to select the ndef file. the ndef file is selected when this co mmand returns "command completed" in the r- apdu. table 26 defines the c-apdu of the select comma nd to select the ndef file (called ndef select). table 24. c-apdu of the capability container select command name cla ins p1 p2 lc data le 0x00 0xa4 0x00 0x0c 0x02 0xe103 - class byte select instruction code p1 field p2 field number of bytes of data cc file id (empty field) table 25. r-apdu of the capability container select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 file or application not found value - 0x6d 0x00 class not supported table 26. c-apdu of th e ndef select command name cla ins p1 p2 lc data le 0x00 0xa4 0x00 0x0c 0x02 0x0001 - class byte select instruction code p1 field p2 field number of bytes of data 0x0001: ndef file (empty field)
docid026583 rev 2 29/51 SRTAG2KL rf command sets table 27 defines the r-apdu of the ndef select command. note: for further return code s and definitions, refer to section 5.6.2: status and error codes . 5.6.6 system file select command the rf host uses this command to select the system file. the system file is selected when this co mmand returns "command completed" in the r- apdu. table 28 defines the c-apdu of the command to se lect the system file (called system select). table 29 defines the r-apdu of the sy stem file select command. note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . table 27. r-apdu of the ndef select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 file or application not found table 28. c-apdu of the system file select command name cla ins p1 p2 lc data le 0x00 0xa4 0x00 0x0c 0x02 0xe101 - class byte select instruction code p1 field p2 field number of bytes of data system file id (empty field) table 29. r-apdu of the system file select command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x6a 0x82 system file not found, no data is returned
rf command sets SRTAG2KL 30/51 docid026583 rev 2 5.6.7 readbinary command on receiving the readbinary command, the SRTAG2KL reads the requested memory field and sends back its value in the r-apdu response. before sending a readbinary command, a file shall be selected by using a select command. the response of the readbinary command is su ccessful when the data to be read is within the selected file (a) ; in other words, when the sum of p1-p2 and le fields is equal to or lower than the selected file length. table 30 defines the readbinary command. table 31 defines the r-apdu of the readbinary command. note: for further return code s and definitions, refer to section 5.6.2: status and error codes . a. for more details about cc file, refer to section 3.1.2: cc file layout . for more details about ndef file, refer to section 3.1.3: ndef file layout . for more details about system file, refer to section 3.1.4: system file layout . table 30. c-apdu of the readbinary command name cla ins p1 & p2 lc data le 0x00 0xb0 2 bytes - - 1 byte class byte read instruction code offset in the file selected (empty field) (empty field) number of bytes to read between 0x01 le max(selected file length, 0xffh) table 31. r-apdu of the readbinary command data sw1 sw2 comment length - 1 byte 1 byte - value content read 0x90 0x00 command completed value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6e 0x00 -
docid026583 rev 2 31/51 SRTAG2KL rf command sets 5.6.8 updatebinary command on receiving the updatebinary command, the SRTAG2KL writes the data field into the selected file and sends back a status in the r- apdu response. if needed, SRTAG2KL will request a timing extension (see section 5.4 ). before sending an updatebinary command, a file shall be selected by issuing a select command. table 32 defines the updatebinary command. note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . table 33 defines the r-apdu of the updatebinary command. note: for further return code s and definitions, refer to status and error codes . table 32. c-apdu of the updatebinary command name cla ins p1 & p2 lc data le 0x00 0xd6 2 bytes 1 byte lc bytes - class byte write instruction code offset in the file selected number of bytes of data (0x01 lc 0xf6) data to write in the SRTAG2KL memory (empty field) table 33. r-apdu of the updatebinary command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x65 0x81 unsuccessful updating value - 0x67 0x00 - value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6e 0x00 -
rf command sets SRTAG2KL 32/51 docid026583 rev 2 5.7 iso/iec 7816-4 commands the iso/iec 7816-4 command set offers some ext ended features such as the protection of the ndef file. this command set is used to ma nage the right access of the ndef file. 5.7.1 verify command the verify command has two functions: 1. check if a password is required to access to the ndef file (the lc field = 0x00). 2. check that the password embedded in the verify command allows the access to the memory (the lc field = 0x10 and the password is present). when the lc field if equal to 0x00, the verify command returns a success code (0x90 00) provided that the access to the ndef file does not require a password. when the access to the ndef file is protected, the response to the verify command returns an error code (0x63 00). when the lc field equals 0x10, on receiving the verify command, the SRTAG2KL compares the requested password with the data containe d in the request and reports whether the operation has been successful in the response. before sending this command, an ndef file shall be selected by issuing the ndef select command. thus, this command checks the righ t access condition of the last ndef file selected. after a successful command, an access is granted for the whole ndef file. table 34 defines the verify command. table 34. verify command format name cla ins p1 & p2 lc data le 0x00 0x20 2 bytes 1 byte lc bytes - class byte instruction code password identification 0x0001: read ndef password transmit 0x0002: write ndef password transmit other: rfu (1) 1. return error code when used. 0x00: the password is not present 0x10: the password is present in the data field password (empty field)
docid026583 rev 2 33/51 SRTAG2KL rf command sets table 35 defines the r-apdu of the verify command. note: for further return code s and definitions, refer to section 5.6.2: status and error codes . 5.7.2 change reference data command the change reference data command replaces the read or write password related to the ndef files previously selected. it can be perform ed only if the security status satisfies the security attributes for this command. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command changes the reference data of the ndef file. table 36 defines the change reference data command. table 36. change reference data command format table 35. r-apdu of the verify command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x84 the conditions of use are not satisfied (e.g. no ndef file was selected or write access equal to ffh (write lock) or read access equal to feh (read lock) value - 0x69 0x81 cmd incompatib le with file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 incorrect para meter in cmd data field value - 0x63 0x00 a password is required value - 0x63 0xcx (1) 1. at each session, the rf host can check a password 3 times. the password transmitted is incorrect and x encodes the number of further allowed retries. name cla ins p1 & p2 lc data le 0x00 0x24 2 bytes 0x10 lc bytes - class byte instruction code password identification 0x0001: read password transmit 0x0002: write password transmit other: rfu (1) 1. return error code when used. 0x10: the password is present in the data field ndef new file password (empty field)
rf command sets SRTAG2KL 34/51 docid026583 rev 2 table 37 defines the r-apdu of the change reference data command. note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . 5.7.3 enable verification requirement command the enable verification requirement command activates the protection by password of the ndef file. when this command is successful, the read or write access to the ndef file is protected by a 128-bit password. it can be performed only if the security status satisfies the security attributes for this command. this command can update the right access of the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 5 ms. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command chan ges the access right of the ndef file. table 38 defines the enable verification requirement command. table 37. r-apdu of the chan ge reference data command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the access right has been changed value - 0x69 0x81 cmd is incompatible with the file structure value - 0x65 0x81 unsuccessful updating value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 incorrect pa ram. in file structure value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values table 38. enable verificati on requirement command format name cla ins p1 & p2 lc data le 0x00 0x28 2 bytes - - - class byte instruction code new security attributes 0x0001: enable the read prot ection of the ndef file 0x0002: enable the write protection of the ndef file other: rfu (empty field) (empty field) (empty field)
docid026583 rev 2 35/51 SRTAG2KL rf command sets the last five bits identify the pa ssword sent in the verify command. table 39 defines the r-apdu of the enable verification requirement command. note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . 5.7.4 disable verification requirement command the disable requirement command deactivates the protection by password of the ndef file. when this command is succe ssful, the read or write access to the ndef file is granted without security requirements. it can be performed only if the security status satisfies the security attributes for this command. before sending this command, the verify command with the correct ndef write password shall be issued. thus, this command chan ges the access right of the ndef file. this command can update the right access of the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 6 ms. table 40 defines the disable verification requirement command. table 41 defines the r-apdu of the disable verification requirement command. table 39. r-apdu of the enable verification requirement command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x81 cmd is incompat ible with the file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 incorrect param. in cmd data field value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values table 40. disable verificati on requirement command format name cla ins p1 & p2 lc data le 0x00 0x26 2 bytes - - - class byte instruction code new security attributes 0x0001: disable the read prot ection of the ndef file 0x0002: disable the write protection of the ndef file other: rfu (empty filed) (empty filed) (empty filed)
rf command sets SRTAG2KL 36/51 docid026583 rev 2 note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . 5.8 st proprietary command set the rf host can be issued with the command set described in this chapter. 5.8.1 extendedreadbinary command on receiving the extendedreadbinary comma nd, the SRTAG2KL reads the requested memory field and sends back its value in the r-apdu response. before sending an extendedreadbinary command, a file shall be selected by issuing an ndef select command. the response of the extendedreadbinary comm and will be successful even if the data to be read is beyond the ndef message. the command returns an error code if the data to be read goes beyond the end of the file. table 43 defines the r-apdu of the read binary command. table 41. r-apdu of the disable verification requirement command data sw1 sw2 comment length 0 1 byte 1 byte - value - 0x90 0x00 command completed, the password is correct value - 0x69 0x81 cmd is incompatible with the file structure value - 0x69 0x82 security status not satisfied value - 0x6a 0x80 cc file or system file selected value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values value - 0x65 0x81 update failed table 42. c-apdu of the extendedreadbinary command name cla ins p1 & p2 lc data le 0xa2 0xb0 2 bytes - - 1 byte st class byte read instruction code offset in the file selected (empty field) (empty field) number of bytes to read between 0x01 le 0xff
docid026583 rev 2 37/51 SRTAG2KL rf command sets note: note: for further return codes and definitions, refer to section 5.6.2: status and error codes . 5.8.2 enablepermanentstate command the command configures the ndef file to the readonly or to the writeonly state. this command can update the right access to the ndef file by writing into the eeprom. in this case, the re sponse timing will be around 6 ms. table 44 defines the enablepermanentstate requirement command. table 45 defines the r-apdu of the enablepermanentstate command. table 43. r-apdu of the extendedreadbinary command data sw1 sw2 comment length le bytes 1 byte 1 byte - value content read 0x90 0x00 command completed value - 0x67 0x00 wrong length value - 0x69 0x82 security status not satisfied value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values table 44. enablepermanentstate command format name cla ins p1 & p2 lc data le 0xa2 0x28 2 bytes - - - class byte instruction code new security attributes 0x0001: lock the ndef file in read mode 0x0002: lock the ndef file in write mode other: rfu (empty field) (empty field) (empty field) table 45. r-apdu table of the enablepermanentstate command data sw1 sw2 comment length - 1 byte 1 byte - value - 0x90 0x00 command completed value - 0x65 0x81 update failed value - 0x69 0x82 security status not satisfied
rf command sets SRTAG2KL 38/51 docid026583 rev 2 note: for further return code s and definitions, refer to section 5.6.2: status and error codes . 5.9 specific rf command set this section describes the command set that can be issued only by the rf host. 5.9.1 anticollision command set table 46 lists the commands that can be issued only by the rf host. the format of these commands is described in the nfc fo rum digital protocol specification. note: in response to a sdd_re q command with a sel_par value equal to 20h, SRTAG2KL in the operating field transmit the requested ca scade level of their nfcid1 (nfcid1 cln, with n=1 or 2). the nfcid1 of SRTAG2KL consis ts of 7 bytes. the length of the response containing a complete nfcid1 cascade level (i.e ., nfcid1 cl1, or nfcid1 cl2) is always 5 bytes. the coding of the response depends on the value of the sel_cmd byte and the size of the nfcid1. refer to example below for more details . value - 0x6a 0x82 file or application not found value - 0x6a 0x86 incorrect p1 or p2 values table 45. r-apdu table of the enablepermanentstate command (continued) data sw1 sw2 comment table 46. commands issues by the rf host family command set comma nd name instruction code nfc-a technology all_req 0x52 (1) 1. code on 7 bits. sens_req 0x26 (1) sdd_req 0x93 or 0x95 sel_req 0x93 or 0x95 slp_req 0x50 table 47. example of anticollision sequence command code comment response code comment sens_req or all-req 26 - atqa 42 00 uid double size bit frame anticollision 52 sdd_req 1 93 20 nvb 20 number valid bit (2 bytes code & nvb) ct uid1 uid2 uid3 bcc ct cascade tag ?0x88? (uid 7bytes) bcc block check character (xor previous bytes)
docid026583 rev 2 39/51 SRTAG2KL rf command sets 5.9.2 rats comma nd and ats response rats command and ats response are used for nfc forum type 4a tag platform device activation (as defined in nfc foru m digital protocol specification). table 48 details the rats command. this command shall be se nt after the anticollision process. sel_req 1 93 70 ct uid1 uid2 uid3 bbc nvb 70 (cmd nvb uid lower bytes) ct cascade tag ?0x88? sak & crc 04 dad7 uid not complete sdd_req 2 95 20 nvb 20 number valid bit (2 bytes code & nvb) - uid4 uid5 uid6 uid7 bcc (uid 7bytes) bcc block check character (xor previous bytes) sel_req 1 95 70 uid4 uid5 uid6 uid7 bbc nvb 70 (cmd nvb uid upper bytes) sak & crc 20 fc70 uid complete table 47. example of anticollision sequence (continued) command code comment response code comment
rf command sets SRTAG2KL 40/51 docid026583 rev 2 the fsdi field codes the fsd that defines the maximum size that an rf host is able to receive. table 49 gives the conversion from fdsi to fsd. the did field defines the value of the addressed SRTAG2KL. the fsci codes the fsc which stands for the maximum frame size that the SRTAG2KL is able to receive. the SRTAG2KL is able to re ceive up to 64 bytes of command. if the rf host sends a command with more than 64 bytes, the SRTAG2KL will not be able to treat the command and will not reply. the fwi which stands for the frame waiting time integer codes the fwt. this time corresponds to the maximum duration while an rf host shall send before sending the next command. table 48. rats command name ins param crc byte field 0xe0 1 byte 2 bytes bit field b7-b4 b3-b0 instruction code fsdi did (0 did 14) 2 crc bytes table 49. conversion from fdsi to fsd fsdi 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9h- 0xe 0xf fsd 16 24 32 40 48 64 96 128 256 rfu 256 table 50. ats response name tl t0 ta(1) tb(1) tc(1) crc byte field 0x05 0x75 0x80 0x60 0x02 2 bytes bit field b8-b5 b4-b1 length of the ats response fsci = 5 => fsc = 64 bytes the maximum ascending data rate is 106 kbps the maximum descending data rate is 106 kbps fwi field (fwi = 6 => fwt = 19.2 ms) sfgi field (sfgi = 0 => sfgt =302 s) the did is supported 2 crc bytes
docid026583 rev 2 41/51 SRTAG2KL rf command sets the sfgi which stands for the start-up fram e guard time is the minimum time that the reader shall wait after receiving the response of the SRTAG2KL. 5.9.3 pps comm and & response (b) pps (protocol and parameter se lection) command a nd response are defined in iso/iec 14443-4, in the protocol activation of picc type a. the pps command allows to change the da ta rates of the a scending (rf host to SRTAG2KL) and descending (SRTAG2KL to rf hos t) data rates. usage of this command is optional, SRTAG2KL only supports 106 kb/s in both direction. the ascending and descending data rates shall be coded as described in table 52 . when the SRTAG2KL is able to change both data rates, it returns the following response. the data rate of this response is 106 kbps; then, the SRTAG2KL changes the ascending and descending data rates. table 53 gives the details sof the pps response. b. not useful in case of SRTAG2KL which only support a data rate of 106 kb/s in both direction. table 51. pps command - name ins (ppss) pps0 pps1 crc byte field 0xdx 0x11 1 byte 2 bytes bit field b7-b4 b3-b0 0b0000 b3-b2 b1-b0 ins instruction code did pps1 is present pps1 rfu descending data rate (106 kb/s) = 0b00 ascending data rate (106 kb/s) = 0b00 2 crc bytes table 52. ascending and descending data rate coding value 0b00 0b01 0b10 0b11 data rate 106 kbps rfu rfu rfu
rf command sets SRTAG2KL 42/51 docid026583 rev 2 table 53. pps response name response (ppss) crc byte field 0xdx 2 bytes bit field b8-b5 b4-b1 response code did field 2 crc bytes
docid026583 rev 2 43/51 SRTAG2KL rf device operation 6 rf device operation 6.1 anticollision and device acti vation command set for the rf interface the SRTAG2KL device supports the command set defined in the nfc-a technology and the type 4a tag platform chapters of th e nfc digital protocol v1.0 specification. 6.2 open an rfsession once the rf host has terminated the ant icollision procedure and re trieve the at s response, it shall send the selectapplication command . the SRTAG2KL will open an rf session. at this point, the rf host can send the applicative command set. 6.3 close an rfsession the rf host can close the rf session by issuing one of these methods: ? send an s(des) command ? turn off the rf field 6.4 applicative command set the applicative command set is composed of the following command sets: ? the nfc forum type 4 tag command set ? the iso/iec 7816-4 command set ? the proprietary command set
functional procedures SRTAG2KL 44/51 docid026583 rev 2 7 functional procedures this section describes some procedure to access the memory or manage its protection. 7.1 selection of an ndef message the rf host shall use this procedure to detect the ndef message inside an SRTAG2KL. the ndef detection procedure is as follows: 1. open an rf session 2. send the selectnd eftagapplication command 3. select the cc file 4. read the cc file 5. select the ndef file. 7.2 reading of an ndef message the rf host executes the ndef re ad procedure to read the ndef file. 1. detect successfully t he ndef file using the ndef detection procedure 2. check that the read access without any security is gr anted for the ndef file from the information provided by the cc file 3. select the ndef file 4. read the ndef file. 7.3 reading a locked ndef file the rf host executes this procedure to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. present the read password by using the verify command 4. read the data in the ndef file. 7.4 locking an ndef file the rf host executes this procedure to protect an ndef file. 1. select the ndef tag application 2. check the right access provided by the cc file 3. select the ndef file 4. present the ndef file write password by using the verify command 5. lock the ndef file by sending the enable verification command.
docid026583 rev 2 45/51 SRTAG2KL functional procedures 7.5 unlocking an ndef file the rf host executes this procedure to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. present the ndef file write pa ssword by using the verify command 4. unlock the ndef file by sending the disable verification command. 7.6 reaching the read-onl y state for an ndef file the rf host executes this procedure to read an ndef file which has been locked previously. 1. select the ndef tag application 2. select the ndef file 3. transmit the ndef file write password by using the verify command 4. send an enablepermanentstate command. 7.7 changing a file type procedure the rf host executes this procedure to change the file type of a file for which all access rights were previously granted. 1. select the ndef tag application 2. select the file to be modified 3. set the file length to 0x00 using the updatebinary command 4. send an updatefiletype command with the new file type as data.
uid: unique identifier SRTAG2KL 46/51 docid026583 rev 2 8 uid: unique identifier the SRTAG2KL is uniquely identified by a 7 bytes unique identifier (uid). the uid is a read- only code and comprises: ? the ic manufacturer code on 1 byte (0x02 for stmicroelectronics). ? the product code on 1 byte. ? a device number on 5 bytes. table 54 describes the uid format. table 54. uid format 0x02 0xe2 5 bytes ic manufacturer code SRTAG2KL product code device number
docid026583 rev 2 47/51 SRTAG2KL maximum rating 9 maximum rating stressing the device ab ove the rating listed in table 55 may cause permanent damage to the device. these are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specif ication is not implied. exposure to absolute maximum rating conditions for extended periods may affect the device reliability. table 55. absolute maximum ratings symbol parameter min. max. unit t a ambient operating temperature -40 85 c t stg , h stg , t stg storage conditions sawn wafer on uv tape 15 25 c 6 (1) 1. counted from st shipment date. months kept in its original packing form t stg storage temperature sawn bumped wafer (kept in its antistatic bag) 15 25 c storage time 6 months i cc (2) 2. based on characterization, not tested in producti on. maximum absorbed power = 100 mw @ 7.5 a/m rf supply current ac0 - ac1 - 100 ma v max_1 (2) rf input voltage amplitude between ac0 and ac1, v ss pad left floating vac0-vac1 (peak to peak) -10v v esd electrostatic discharge voltage (human body model) (3) 3. aec-q100-002 (compliant with jedec std jesd22-a114a, c1 = 100 pf, r1 = 1500 , r2 = 500 ) ac0-ac1 - 1000 v
rf electrical pa rameters SRTAG2KL 48/51 docid026583 rev 2 10 rf electrical parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in rf mode. the parameters in the dc and ac characterist ics tables that follow are derived from tests performed under the measurement conditi ons summarized in the relevant tables. designers should check that the operating cond itions in their circuit match the measurement conditions when relying on the quoted parameters. table 56. default operating conditions symbol parameter min. max. unit t a ambient operating temperature ?40 85 c table 57. rf characteristics (1) symbol parameter condi tion min typ max unit f c external rf signal frequency 13.553 13.56 13.567 mhz h_iso operating field according to iso t a = 0 c to 50 c 1500 - 7500 ma/m h_extended operating field in extended temperature range t a = -40 c to 85 c 100 - 7500 ma/m h min field detect, set-up field (1) t a = -40 c to 85 c - 50 - ma/m mi carrier 100% carrier modulation index mi=(a-b)/(a+b) 90 - 100 % t 1 pause a length - 28/f c - 40.5/f c s t 2 pause a low time - 7/f c -t1s t 3 pause a rise time - 1.5xt4 - 16/f c s t 4 pause a rise time section - 0 - 6/f c s t min cd minimum time from carrier generation to first data from h-field min - - 5 ms w t rf write time (including internal verify) for one page - - 4.468 (2) -ms c tun /5 (3) internal tuning capacitor (4) f c = 13.56 mhz 45 50 55 pf t rf_off rf off time chip reset - - 0.1 ms 1. all timing characterizations were performed on a re ference antenna with the fo llowing char acteristics: external size: 75 mm x 48 mm number of turns: 4 width of conductor: 0.5 mm space between two conductors: 0.5 mm value of the tuning capacitor: 50 pf (SRTAG2KL) value of the coil: 2.5 h tuning frequency: 14.2 mhz. 2. time between command eof and response sof when updating ndef message length 3. see /5 = 50 pf . 4. characterized only, at room temperature only, m easured at vac0-vac1 = 2 v peak to peak at 13.56 mhz.
docid026583 rev 2 49/51 SRTAG2KL part numbering 11 part numbering note: parts marked as ?es?, ?e? or accompanied by an engineering sample notification letter, are not yet qualified and therefore not yet ready to be used in production and any consequences deriving from such usage will not be at st char ge. in no event, st wi ll be liable for any customer usage of these engineering samples in production. st quality has to be contacted prior to any decision to use these engineering samples to run qualification activity. table 58. ordering information scheme for packaged devices example: srtag 2k l- sb12 /5 device type srtag = short range tag memory size 2k = memory size in kbits device feature l- = tag (no digital output) package mh = ufdfpn5 sb12 = 120 m 15 m bumped and sawn inkless wafer on 8-inch frame device grade 6 = industrial: device tested with sta ndard test flow over ?40 to 85 c (no parameter for sb12) option t = tape and reel packing (no parameter for sb12) capacitance /5 = 50 pf
revision history SRTAG2KL 50/51 docid026583 rev 2 12 revision history table 59. document revision history date revision changes 28-oct-2014 1 initial release. 16-jan-2015 2 added note and updated table 58: ordering information scheme for packaged devices
docid026583 rev 2 51/51 SRTAG2KL important notice ? please read carefully stmicroelectronics nv and its subsidiaries (?st?) reserve the right to make changes, corrections, enhancements, modifications, and improvements to st products and/or to this document at any time without notice. purchasers should obtain the latest relevant in formation on st products before placing orders. st products are sold pursuant to st?s terms and conditions of sale in place at the time of o rder acknowledgement. purchasers are solely responsible for the choice, selection, and use of st products and st assumes no liability for application assistance or the design of purchasers? products. no license, express or implied, to any intellectual property right is granted by st herein. resale of st products with provisions different from the information set forth herein shall void any warranty granted by st for such product. st and the st logo are trademarks of st. all other product or service names are the property of their respective owners. information in this document supersedes and replaces information previously supplied in any prior versions of this document. ? 2015 stmicroelectronics ? all rights reserved

▲Up To Search▲

Price & Availability of SRTAG2KL

	To Download SRTAG2KL Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .